Deploying Legacy Windows and DOS Apps

For legacy Windows 95/98/ME and DOS applications, the supported protection is Machine License only. The needed system files include the KeyCheck library (16-bit or 32-bit DLL) and the ElecKey agent for Local Key (legacy OS version). The table below lists the needed system files. These system files must be placed in the same folder as the protected executable.

Application Type : OS	System Files	Available in Directory
DOS	No system file needed	-
Win16 : Windows 3.x	EKC1620.DLL	\DEPLOY\WIN16APP\KEYCHECK
Win32/.NET : Windows 95/98/ME	EKC3220.DLL, XKC3220.DLL, EKAG20.EXE	\DEPLOY\WIN32APP\KEYCHECK

NOTE: The protected application based on DOS and Windows 3.x can interface with the Key without requiring the ElecKey agent. In case of Win16 applications, only EKC1620.DLL is needed.

NOTE: The protected DOS application supports the Key with Ethernet adapter signature enabled. However, the user must have the network device drivers loaded properly. For example, loading LSL.COM (Link Support Layer) followed by IPXODI.COM for the IPX protocol, or followed by NETBIOS.EXE for NetBIOS emulation.

NOTE: The protected Win16 application does not support the Key with Ethernet adapter signature enabled.

NOTE: The ElecKey agent EKAG20.EXE (legacy OS version) needs an additional file XKC3220.DLL to interface with the Key with Ethernet adapter signature enabled.

NOTE: If your protected application will be deployed on different platforms ranging from Windows legacy (95/98/ME) to modern (NT/2000/XP/2003/ vista/7/8 (x86/x64)) operation systems, you should include both versions of the ElecKey agent (EKAG20NT.EXE and EKAG20.EXE). The protected application can automatically detect the operating system and use the appropriate agent.

See Also

· End-User Utilities